Automatic synchronization of a device for transaction processing based on geo-fenced locations

ABSTRACT

There are provided systems and methods for automatic synchronization of a device for transaction processing based on geo-fenced locations. A merchant may geo-fence an area corresponding to the merchant&#39;s location where a user may visit to purchase an item. The merchant may provide multiple transaction processing and payment options at the merchant location, including payment applications with a mobile communication device. A payment provider may detect the location of the user and determine that the user&#39;s location matches the merchant&#39;s location through the geo-fenced area for the merchant. The payment provider may then configure a payment process for the user to utilize at the merchant location using payment mechanisms accepted at the merchant location. Where multiple merchants are located nearby, the payment provider may utilize additional known information for the user to select the most likely merchant for the user.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/807,098, filed on Mar. 2, 2020, which is a continuation ofU.S. patent application Ser. No. 15/284,397, filed on Oct. 3, 2016, nowU.S. Pat. No. 10,579,985, which claims priority to U.S. ProvisionalPatent Application Ser. No. 62/236,087, filed on Oct. 1, 2015, which isincorporated by reference in their entirety.

TECHNICAL FIELD

The present application generally relates to electronic paymentmechanisms and more specifically to automatic synchronization of adevice for transaction processing based on geo-fenced locations.

BACKGROUND

Users may engage in transactions with merchants in order to purchaseitems. Traditionally, users were limited to physical payment mechanisms,which included cash or check. Modernly, credit cards and communicationtechnologies have further allowed for additional payment instruments tobe used at merchants that possess the proper acceptance mechanisms.However, as technology advances, payment mechanisms used in transactionsmay involve further processes, and merchants may begin to install orpossess the proper infrastructure of various other types of paymentinstruments or mechanisms to effectuate a payment for a transaction. Forexample, near field communications (NFC) may allow a user to pre-load orrequest tokenized data that may be communicated to a merchant device forresolution by “tapping” or placing a communication device having thetokenized data near an NFC device for the merchant. Other methods ofpayment may also be accepted at certain merchants where the merchantpossesses the proper acceptance mechanisms and tools. However, withoutbeing aware of the acceptance mechanism available with a merchant or atthe merchant's location, the user may choose a merchant where the usercannot complete a transaction using the available payment tools to theuser. Additionally, the user may encounter more friction choosing theproper payment tool to use with the merchant without knowledge of themerchant's acceptance mechanisms.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2 is an exemplary geo-fenced merchant location to provide a userexperience on a mobile device, according to an embodiment;

FIG. 3 is an exemplary system environment having a communication deviceconfigured to payment processing with a merchant device by a paymentprovider server based on accepted payment mechanisms for the merchantdevice, according to an embodiment;

FIG. 4 is an exemplary process flowchart for automatic synchronizationof a device for transaction processing based on geo-fenced locations,according to an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1 , according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods utilized for automatic synchronization of a devicefor transaction processing based on geo-fenced locations. Systemssuitable for practicing methods of the present disclosure are alsoprovided.

A payment provider may offer account services to various entities, whichmay include personal users and groups of users (e.g., companies), aswell as merchants. The accounts with the payment provider may correspondto payment accounts, where a holder of the account may send and receivepayments and otherwise engage in financial transactions. In order toestablish a payment account, the payment provider may requireinformation from the user, which may be stored as user data. Theinformation may include personal and financial information, as well asother information that may be determined or requested from the user,including demographic information, preferences, interests, historicalinformation, education, work, etc. Additionally, the user may specifyauthentication credentials, such as a login name, password, and/orpersonal identification number (PIN) for use of the payment account. Thepayment account may further be associated with a payment applicationexecuting on a communication device of the user. In various embodiments,the payment application may generally correspond to a web browserapplication accessing a website of the payment provider to processpayments, or may correspond to a dedicated application of the paymentprovider executing on the communication device. Moreover, thecommunication device may include various payment processing componentsthat may be used when processing payments with another device, such as amerchant device. Such payment processing components may include acommunication module to provide short range wireless communications(e.g., Bluetooth Low Energy (BLE), Bluetooth, near field communications(NFC), WiFi, LTE Direct, radio, infrared, etc.) with a merchant, forexample, to effectuate a check-in and/or provide a token. Otherprocessing components may include an output display to display a barcodeor QR code (e.g., having encoded payment information in the barcode orQR code, which may be encoded into the QR code or barcode by a paymentapplication or a payment provider) and/or a GPS locator to associate thegeo-location of the user with a geo-fenced area for a merchant.

A user may also generate user data, such as user actions of the user,which may be collected and stored by one or more devices of servers. Theuser data may therefore include user locations, travel routes, physicalactivity, or other data associated with where a user may be located at aspecific time or during specific time periods. Additionally, thegenerated user data may correspond to transactions engaged in by theuser with one or more merchants. The user data may include user searchhistories and other information indicating potential purchases ormerchants of interest to the user. A service provider may collect dataassociated with the user's online transactions, social networkinginteractions, messages, connections, loyalty program information, and/orother available online actions by the user. Additionally, the user'scommunication device may generate user data corresponding to the user,which may include the user's personal/financial information, location(which may be determined in conjunction with a GPS locator of the user'scommunication device or other location determining system), biometrics,communications, etc. Such information may be used to generate pasthistorical information and tendencies of the user, which may be usefulfor determining user interests, habits, and/or other defininginformation that may be used to determine a merchant location that theuser may visit.

The payment provider may provide one or more types of paymentinstruments to a user through a digital wallet and accessible using thepayment application of the communication device, which may be utilizedby the user to pay for and complete a transaction with a merchant havingacceptance mechanism(s) that match the payment instruments. Types ofpayment instruments may include payment accounts with the paymentprovider, financial accounts with other financial institutions,credit/debit cards, gift cards, and other types of funding sources. Thepayment application may utilize different interfaces and/or processes inorder to provide and/or process each type of payment instrument for atransaction between the user and a merchant, and may utilize variouscomponents of the communication device in order to provide paymentprocessing, such as the communication module, GPS locator, and/ordisplay device.

These payment instruments may be used in a transaction throughacceptance mechanisms that the merchant uses for acceptance of thepayment mechanism. Acceptance mechanisms may include tokenized paymentsusing a token that identifies data necessary to conduct a transaction.In this regard, a token may correspond to an identifier that identifiesa user, a user account (e.g., a payment account with a paymentprovider), a payment instrument, a digital wallet (e.g., a digitalrepresentation of one or more payment instruments, or other entity thatmay provide a payment to a merchant. For example, a token may include anemail address, account name, or other data element that representssomething to be used for payment processing. The token may becommunicated through an encrypted or unencrypted data transmissionbetween a device for the user and a device for the merchant, which maybe effected through near field communications, Bluetooth, Bluetooth LowEnergy (BLE), WiFi, radio, magnetic field emissions, infrared, or othershort range wireless technology. The merchant may perform paymentprocessing using a received token, for example, by communicating thetoken with transaction information to a payment provider, which mayprocess a payment to the merchant using the token (e.g., throughidentification of the user's account, payment instrument, digitalwallet, etc.). Additionally, acceptance mechanisms used to acceptpayment information for a payment instrument used in a transaction mayinclude scanning or otherwise entering a displayed code (e.g.,alphanumeric, bar, image, and/or QR code) on a merchant device by theuser's device, displaying a code on the user's device for entry to themerchant device, and location based check-in of the user for propagationof the merchant's information within a payment application and/orpropagation of the user's information on a sales application of themerchant device. In such embodiments, a token may also correspond to themerchant, location, transaction, or other data necessary to identify themerchant and/or transaction, and provide a payment to the merchant for atransaction. Thus, a token in this respect may be entered to the userdevice and communicated to a payment provider for processing, which mayfurther include transaction information where necessary.

For example, and as discussed herein, a check-in may correspond to aprocess associating the user with a specific location, such as amerchant location. The check-in process may be accomplished throughdetection of a geo-location of the user, which may utilize the GPSlocator of the communication device or may allow the user to self-checkin through selection of the merchant location or entering a location(e.g., location name, address, coordinates, etc.). In such embodiments,the payment provider may receive the user's geo-location and use a maphaving geo-fenced areas for merchants to determine a merchant for theuser's geo-location by determining if the user's geo-location matches(e.g., is found within) a geo-fenced area for a merchant. The merchantmay further break up a geo-fenced area into smaller geo-fenced areaseach corresponding to a particular item offered by the merchant, such asa grocery store section, a particular gas pump at a gas station, and/ora particular merchant at a department store. The check-in may also beaccomplished through short range wireless communications with a deviceat the merchant location, which may provide an identifier for the userto the device at the merchant location and/or retrieve a merchantidentifier for the merchant from the device at the merchant location.Once checked-in, the user may be associated with the merchant locationand one or more processes of the communication device and/or a paymentprovider server may provide user information to a merchant device forthe merchant location or retrieve merchant information for use with thecommunication device.

Merchants may accept one or more of these acceptance mechanisms, whichmay allow the user to provide payment to the merchant using one or morepayment instruments through the payment provider. For example, where awallet token that identifies a digital wallet (e.g., with a paymentprovider) is communicated to a device for the merchant, the merchant mayprovide the wallet token to the payment provider for processing, whichmay be transmitted with transaction information. Once received, thepayment provider may utilize the wallet token to identifier a paymentaccount and any payment instruments stored to a digital wallet, andprovide payment to the merchant using the merchant's acceptancemechanism(s) for payment. The acceptance mechanism may also be merchantspecific and/or specific to a particular device at a merchant location.For example, a user may be associated with a gas station such that theuser may effectuate a payment at a fuel pump where the fuel pump ispreloaded with the user's information. In such embodiments, the gasstation may geo-fence the fuel pump so that the user is detected at aparticular gas pump and/or request that the user provide information atthe fuel pump to identify the user or payment account. In otherembodiments, the acceptance mechanism(s) for the merchant location mayinclude a sale through tokenized payments using short range wirelesscommunications (e.g., exchange of a token through short range wirelesscommunications) or a token encoded to a barcode or QR code displayed bythe communication device or the merchant device (e.g., a token identifya payment account, payment instrument, digital wallet, etc. displayed bya communication device, or a token identifying a merchant, merchantlocation, transaction, etc., displayed by a merchant device).

Thus, in order to select a user experience that assists the user inproviding payment through the merchant's acceptance mechanism, thepayment provider may use current user data and other availableinformation to determine a merchant that the user may engage in atransaction with and which acceptance mechanism(s) the merchantutilizes. In various embodiments, the user may opt-in to allow thepayment provider to utilize location based services to determine alocation of the user. The payment provider may receive the location ofthe user (e.g., from a GPS locator of the communication device) and maymatch the location to a merchant. Geo-fences may be created at or arounda merchant location, so that when the user's location crosses into ageo-fence, the user is associated with the merchant for the geo-fencedarea. For example, a geo-fence for a gas station may correspond to theimmediate vicinity surrounding the gas station's property. Thus, as theuser drives into the geo-fence and crosses the border, the user may beassociated with the gas station. In various embodiments, exiting thegeo-fence may disassociate the user with the merchant and/or merchantlocation.

In other embodiments, the user may opt-in to allow short range wirelesscommunications with merchant device (e.g., through BLE and the merchantdevice and/or a corresponding wireless beacon at the merchant location).The user's communication device may then link to the device at themerchant location and perform a check-in of the user, as previouslydiscussed. The check-in may then establish the user at the merchantlocation and/or associated with the merchant device or wireless beaconconnected to the communication device. Using the connection and/orcheck-in, the payment provider may then determine that the merchantassociated with the merchant device or wireless beacon connected to thecommunication device is the merchant that the user may transact with forone or more items available from the merchant.

Additionally, where location based services and/or short range wirelesscommunications are unavailable or the user's location may be associatedwith multiple merchants (e.g., in a crowded shopping mall), additionaluser data and information may be accessed and used to determine themerchant that the user may potentially engage in a transaction with forone or more items. Thus, based on the user's demographic information,the user may be more likely to shop at one merchant over another. Forexample, a single 25 year old male may be more likely to visit a sportsstore than an adjacent baby clothes store. In other embodiments, theuser's history may assist in choosing the merchant location. Thus, if auser is nearby a restaurant that the user commonly visits for food, thatrestaurant may be chosen as the merchant over an adjacent sunglassesstore that the user has never visited. Other past user information,available personal and/or financial information, and/or other user datamay be used to determine the merchant that the user wishes to visit. Invarious embodiments, the user may be presented a menu through agraphical user interface of a device application of the user'scommunication device. The menu selection may have two or more of thenearby merchants that the user may visit. The user may then make aselection of the merchant that the user intends on visiting and maytransact with. The user's selection may be stored for future use whenthe user is at or nearby the same or same types of merchants.Additionally, the merchants populated to the menu interface may includeall nearby merchants, or a subset of nearby merchants that the user mayvisit based on known user information.

Once the merchant that the user may visit and/or transact with isdetermined, the user experience that should be utilized based on themerchant may be further determined. The user experience may correspondto a payment process to utilize the merchant's acceptance mechanism fora payment instrument during a transaction. Thus, the payment providermay determine which acceptance mechanisms are used at the merchantlocation, for example, from known information of the merchant, queryingthe merchant, and/or analysis of past merchant transactions and currentdevice capabilities at the merchant location. Once an acceptancemechanism for the merchant location is determined, a payment processused with the acceptance mechanism may be determined for the user'scommunication device. The payment process may configure the user'scommunication device to utilize the acceptance mechanism. The paymentprocess may be loaded or otherwise configure a device application on thecommunication device, such as a mobile payment application. Thus, if theacceptance mechanism at the merchant location includes a merchant devicethat scans a QR code displayed through a mobile payment application ofthe user's communication device, the payment process may set up theuser's communication device to display a QR code during transactionprocessing. In other embodiments, the acceptance mechanism may configurethe payment application to communicate with a merchant device over shortrange wireless communications, such as NFC to provide an electronictokenized payment. Moreover, the acceptance mechanism may also loadmerchant information to the user's communication device for networkedprocessing of a tokenized payment to the merchant. The communicationdevice may execute a mobile device application that may receive thetransaction details from user input, scanning of another code, ormerchant device communications and receive QR code that may be scannedby the merchant device.

In further embodiments, the payment process may also or insteadconfigure a merchant device at the merchant location. For example, thepayment process may load user information for the user to a merchantdevice at the merchant location so that the merchant device may quicklycheckout and process a payment for the user. The user information mayfurther include a token used to perform payment processing. For example,the user may select and/or be informed of the payment instrument for atransaction at the merchant location, and may provide identificationand/or authentication when processing a transaction through pre-loadedpayment information to a merchant device. Such information may berepresented by a token, which may be communicated to the merchantdevice. In other embodiments, a token may represent a digital wallet,where a cloud computing entity (e.g., a payment provider) selects apayment instrument or allows the user to decide on a payment instrumentfor payment processing (e.g., through a user experience, which may beperformed through an application of the user's device). The merchantdevice may also be configured to communicate with the communicationdevice over short range wireless communications or scan a displayedcode.

In various embodiments, the merchant and/or the payment provider mayfurther provide advertisements and/or coupons to the user for use at themerchant location on detection of the user at the merchant location. Theadvertisements and/or coupons may be communicated to the user throughthe user's communication device and displayed to the user for use duringtransaction processing. Moreover, the payment provider may furtherdetermine a list of nearby merchants, which may be shortened and/orranked based on the most likely merchants that the user may transactwith. Where an initially selected merchant is not correct, the user mayrequest a change of merchant by the payment provider. The paymentprovider may then select a next best matching merchant from nearbymerchants for the user based on the user data and merchant data fornearby merchants. The user may then approve the next merchant or requestfurther search. The payment provider may execute similar steps as thosedescribed above to determine a payment process for the next requestedmerchant and further configure a communication device and/or merchantdevice to process payments. The payment provider may then utilize theinformation on past selected merchants and transactions by the user tointelligently select further prospective merchants transacting with theuser.

Once the payment process is established, the communication device mayutilize the payment process during a transaction with the merchant toprovide payment through the merchant's acceptance mechanism. Themerchant may then receive payment for the transaction using theacceptance mechanism and the payment process. The payment provider mayreceive a payment request to the merchant by the user from use of thepayment process with the acceptance mechanism. The payment provider mayprovide payment to the merchant and/or to an account for the merchantusing the user's payment instrument. Transaction information may includeterms of the payment request. Further, the payment provider may providea transaction history, such as a receipt, to the user and/or merchantfor documenting the transaction. Additionally, while payment processingis occurring, media may be presented to the user, for example, throughthe user's communication device and/or on an output device nearby theuser (e.g., a display device at a gas pump). The media may includeadvertisements, targeted information, and/or other types of audio,visual, and/or audiovisual content.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or other suitable device and/or server based OS.It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such devices and/or servers may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a communication device 110, a transaction managementsystem 130, and a merchant device 150 in communication over a network160. A user (not shown) may establish a payment account with transactionmanagement system 130, which may be used to provide payments to amerchant (not shown) associated with merchant device 150. User data maybe collected and/or determined by transaction management system 130.When the user data indicates that the user may shop with merchant device150, transaction management system 130 may determine an acceptancemechanism by the merchant using merchant device 150 to receive paymentusing the payment account for the user and/or an instrument stored totransaction management system 130. Transaction management system 130 maythen determine a payment process for use with the acceptance mechanism,which may be used to configure communication device 110 to interact withthe acceptance mechanism of merchant device 150 and provide payment.

Communication device 110, transaction management system 130, andmerchant device 150 may each include one or more processors, memories,and other appropriate components for executing instructions such asprogram code and/or data stored on one or more computer readable mediumsto implement the various applications, data, and steps described herein.For example, such instructions may be stored in one or more computerreadable media such as memories or data storage devices internal and/orexternal to various components of system 100, and/or accessible overnetwork 160.

Communication device 110 may be implemented as a communication devicethat may utilize appropriate hardware and software configured for wiredand/or wireless communication with transaction management system 130and/or merchant device 150. For example, in one embodiment,communication device 110 may be implemented as a personal computer (PC),a smart phone, laptop/tablet computer, wristwatch with appropriatecomputer hardware resources, eyeglasses with appropriate computerhardware (e.g. GOOGLE GLASS®), other type of wearable computing device,implantable communication devices, and/or other types of computingdevices capable of transmitting and/or receiving data, such as an IPAD®from APPLE®. Although a communication device is shown, the communicationdevice may be managed or controlled by any suitable processing device.Although only one communication device is shown, a plurality ofcommunication devices may function similarly.

Communication device 110 of FIG. 1 contains a payment application 120, auser data component 112, other applications 114, a database 116, and anetwork interface component 118. Browser/payment application 120 andother applications 114 may correspond to executable processes,procedures, and/or applications with associated hardware. In otherembodiments, communication device 110 may include additional ordifferent modules having specialized hardware and/or software asrequired.

Payment application 120 may correspond to one or more processes toexecute modules and associated devices of communication device 110 toinitiate, receive, and/or process/complete transactions using servicesprovided by transaction management system 130. In this regard, paymentapplication 120 may correspond to specialized hardware and/or softwareutilized by communication device 110 to provide an interface to permitthe user associated with communication device 110 to select paymentoptions and provide payment for items, for example, to a merchantthrough merchant device 150 using transaction management system 130. Invarious embodiments, payment application 120 may also provide paymentsand/or transfers to users and/or groups of users, for example, paymentsto individual sellers or friends for items and/or transfers betweenknown associates. Payment application 120 may be implemented as a userinterface enabling the user to enter payment options for storage bycommunication device 110, select and provide payment options oncheckout/payment of one or more items with a merchant, and complete atransaction for the item(s) through a purchase request for the item(s).In various embodiments, payment application 120 may include a generalbrowser application configured to retrieve, present, and communicateinformation over the Internet (e.g., utilize resources on the World WideWeb) or a private network. For example, payment application 120 mayprovide a web browser, which may send and receive information overnetwork 170, including retrieving website information, presenting thewebsite information to the user, and/or communicating information to thewebsite, including payment information. However, in other embodiments,payment application 120 may include a dedicated application oftransaction management system 130 or other entity (e.g., a merchant),which may be configured to assist in processing purchase requests.

As discussed herein, transaction management system 130 may be used todetermine that the user associated with communication device 110 mayvisit and transact with the merchant associated with merchant device150. Transaction management system 130 may then determine the acceptancemechanism used by the merchant, and may configure payment application120 to utilize the acceptance mechanism during a payment process for atransaction between the user and the merchant. Transaction managementsystem 130 may determine the payment process to use the acceptancemechanism, such as display of a code using payment application 120,imaging a code through communication device 110, establishing a check-infor the user, and/or loading user data (e.g., a token identifying theuser or payment information for the user) to merchant device 150 ormerchant data (e.g., a token identifying the merchant and/or atransaction between the user and a merchant) to payment application 120.Thus, payment application 120 may be configured to provide a payment tomerchant device 150 through display or imaging a QR code, bar code, orother displayable code. In other embodiments, payment application 120may communicate with merchant device 150 for transaction processing overa wireless connection configured by a payment process determine bytransaction management system 130. Once a payment process configurespayment application 120 for transaction processing with merchant device150, the user of communication device 110 may utilize paymentapplication 120 to process a payment for a transaction through one ormore payment interfaces.

Payment application 120 may be utilized to select payment instrument(s)for use during a transaction between the user and the merchantassociated with transaction management system 130. For example, the usermay wish to complete a transaction with a merchant to purchase the item.Payment application 120 may utilize user financial information, such asa credit card, bank account, or other financial account, as a paymentinstrument when providing payment information for use in theauthentication mechanism. In other embodiment, payment application 120may provide a token that identifies the user, a digital wallet, and/or apayment instrument to merchant device 150 for use in transactionprocessing. Additionally, payment application 120 may utilize a useraccount with payment provider, such as transaction management system130, as the payment instrument. The user may therefore generate apayment request to the merchant for one or more items for purchase inthe transaction. The payment request may be communicated to transactionmanagement system 130 for processing. In various embodiments, thepayment request may include a token communicated to transactionmanagement system 130 and/or merchant device 150 for processing, orreceived from merchant device 150. Payment application 120 may beutilized to view the results of the transaction and/or for viewing andstorage of a transaction history, such as a receipt.

User data component 112 may correspond to one or more processes toexecute modules and associated specialized hardware of communicationdevice 110 that may be used to locally track user actions and other userdata for the user and provide the user data to transaction managementsystem 130. In this regard, payment application 120 may correspond tospecialized hardware and/or software utilized by communication device110 to collect, capture, and/or otherwise determine user data for theuser by monitoring the user. The user data may correspond to locationsof the user, which may further be determined using a locationdetermination system, such as a GPS module of communication device 110and associated systems. In other embodiments, the user's actions maycorrespond to biometrics, exercise data, and/or nutritional information,which may be input by the user and/or captured with the assistance of aconnected device, such as a pedometer (e.g., a FITBIT® or similar deviceusing a short range wireless communication with communication device110). The user data may be provided to transaction management system 130for use in determining that the user with visit the merchant associatedwith merchant device 150. In various embodiments, user data component112 may determine the user data provided to transaction managementsystem 130 using other applications and/or processes of communicationdevice 110, including messaging applications (e.g., email, SMS/MMS,instant messaging, and/or social networking messaging), Internetbrowsers, Internet search engines, social networking applications,merchant and shopping applications, travel applications (e.g., travelfare reservation and purchasing applications including air travel, aswell as local travel applications for utilizing subways, taxis, carrentals, and other transportation local to the user), and/or mappingapplications. Additional user data captured by user data component 112may include media viewing applications, video games, word processors andassociated applications, and/or other types of modules, processes, andapplications which may track and/or determine the user's actions. Userdata component 112 may then provide the user actions and other user data(e.g., personal, financial, and other user information) to transactionmanagement system 130 for processing, such as determination of merchantsthat a user may transact with.

In various embodiments, one or more the discussed hardware and/orsoftware features of browser/payment application 120 and user datacomponent 112 may be included in the same module.

In various embodiments, communication device 110 includes otherapplications 114 as may be desired in particular embodiments to providefeatures to communication device 110. For example, other applications114 may include security applications for implementing client-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 160,or other types of applications. Other applications 114 may also includeemail, texting, voice and IM applications that allow a user to send andreceive emails, calls, texts, and other notifications through network160. In various embodiments, other applications 114 may includefinancial applications, such as banking, online payments, moneytransfer, or other applications. Other applications 114 may also includeother location detection applications, such as a mapping, compass,and/or GPS application. Other applications may include social networkingapplications and/or merchant applications. Other applications 114 mayinclude device interfaces and other display modules that may receiveinput and/or output information. For example, other applications 114 maycontain software programs, executable by a processor, including agraphical user interface (GUI) configured to provide an interface to theuser.

Communication device 110 may further include database 116 stored to atransitory and/or non-transitory memory of communication device 110,which may store various applications and data and be utilized duringexecution of various modules of communication device 110. Thus, database116 may include, for example, identifiers such as operating systemregistry entries, cookies associated with browser/payment application120 and/or other applications 114, identifiers associated with hardwareof communication device 110, or other appropriate identifiers, such asidentifiers used for payment/user/device authentication oridentification. Database 116 may include location information and userdata, which may be transmitted to transaction management system 130and/or merchant device 150. A payment process for use with an acceptancemechanism may also be stored to database 116.

Communication device 110 includes at least one network interfacecomponent 118 adapted to communicate with transaction management system130, and/or merchant device 150. In various embodiments, networkinterface component 118 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication devices.

Transaction management system 130 may be maintained, for example, by anonline payment service provider, which may provide payment servicesand/or processing for financial transactions on behalf of users. In thisregard, transaction management system 130 includes one or moreprocessing applications which may be configured to interact withcommunication device 110, merchant device 150, and/or anotherdevice/server to facilitate payment for a transaction, includingestablishment of payment accounts and configuration of mobile deviceapplications to use an acceptance mechanism for electronic payments by amerchant. In one example, transaction management system 130 may beprovided by PAYPAL®, Inc. of San Jose, Calif., USA. However, in otherembodiments, transaction management system 130 may be maintained by orinclude a credit provider, financial services provider, financial dataprovider, and/or other service provider, which may provide paymentservices to the user.

Transaction management system 130 of FIG. 1 includes acceptancemechanism application 140, a transaction processing module 132, otherapplications 134, a database 136, and a network interface component 138.Acceptance mechanism application 140, transaction processing module 132,and other applications 134 may correspond to executable processes,procedures, and/or applications with associated hardware. In otherembodiments, transaction management system 130 may include additional ordifferent modules having specialized hardware and/or software asrequired.

Acceptance mechanism application 140 may correspond to one or moreprocesses to execute modules and associated specialized hardware oftransaction management system 130 to receive and/or transmit informationfrom communication device 110 for use in determining one or moremerchants that the user associated with communication device 110 maytransact with, determining an acceptance mechanism for payment used bythe merchant(s), determining a payment process to configurecommunication device 110 with to use the acceptance mechanism, andconfiguring communication device 110 to use the payment process. In thisregard, acceptance mechanism application 140 may correspond tospecialized hardware and/or software to access user data and determinethat the user associated with communication device 110 may interact withthe merchant associated with merchant device 150 for the purpose ofengaging in a transaction to purchase one or more items. For example,acceptance mechanism application 140 may determine that the user islocated at a merchant location or traveling to the merchant locationbased on location services of communication device 110. In embodimentswhere the user is nearby multiple merchants, past user data,demographics, or other information may be used to determine themerchant. In order to determine that a user is at or nearby a merchantlocation, acceptance mechanism application 140 may access or receivegeo-fencing information for merchants, for example, from merchant data.For example, a geo-location may be detected for the user and foundwithin a geo-fenced area for a merchant (e.g., on a map of merchantseach having geo-fenced areas). Thus, the user may be associated withthat merchant location. In other embodiments, a third party resource mayperform the matching of the geo-location detected by communicationdevice 110 to a geo-fenced area for the merchant associated withmerchant device 150. The merchant data may further include merchantinformation (e.g., type, brand, sales, name, shopper demographics, etc.)in order to determine whether the merchant matches the user.

Once detected at a merchant location, acceptance mechanism application140 may further determine that the merchant utilizes a specificacceptance mechanism. For example, acceptance mechanism application 140may access payment data for the merchant, which may include acceptedpayment mechanisms at the merchant location, such as payment throughbarcode/QR code displays having an encoded token, short range wirelesscommunications and digital tokens, and/or check-in and loading ofuser/merchant information to a payment application for networked paymentprocessing. If the merchant accepts multiple payment acceptancemechanisms, acceptance mechanism application 140 may match theacceptance mechanisms to payment mechanisms utilized by communicationdevice 110. Moreover, a “favorite” or most used payment mechanism of theuser associated with communication device 110 may be selected, or afastest (e.g., payment processing time) acceptance mechanism may beselected. Using the acceptance mechanism, acceptance mechanismapplication 140 may configure payment application 120 of communicationdevice 110 to use the acceptance mechanism in a payment process for atransaction. Payment application 120 may be configured prior to arrivingat the merchant location or engaging in the transaction.

Transaction processing module 132 may correspond to one or moreprocesses to execute modules and associated specialized hardware oftransaction management system 130 to receive and/or transmit informationfrom communication device 110 for establishing payment accounts, as wellas processing and completing of one or more funding transactionsinitiated using the payment accounts. In this regard, transactionprocessing module 132 may correspond to specialized hardware and/orsoftware to establish payment accounts, which may be utilized to sendand receive payments and monetary transfers and engage in otherfinancial transactions. A user associated with communication device 110may establish a payment account with transaction processing module 132by providing personal and/or financial information to transactionmanagement system 130 and selecting an account login, password, andother security information. The payment account may be used to send andreceive payments. The payment account may be accessed and/or usedthrough a browser application and/or dedicated payment applicationexecuted by communication device 110. Transaction processing module 132may receive a payment request from communication device 110 and/ormerchant device 150 for a transaction between the user and the merchant,which may include identifiers, tokens, or other data used fortransaction processing. The payment request may include transactionterms and a token, identifier, authentication information, or other datanecessary for the payment process configured on communication device 110for use with the merchant's acceptance mechanism. Thus, the paymentrequest may be generated by using the payment process with theacceptance mechanism. Transaction processing module 132 may providepayment to the merchant using the payment instrument, and may provide atransaction history to communication device 110, merchant device 150, orstore the history with one or more accounts.

In various embodiments, transaction management system 130 includes otherapplications 134 as may be desired in particular embodiments to providefeatures to payment provider server 134. For example, other applications134 may include security applications for implementing server-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 160,or other types of applications. Other applications 134 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI), configured to provide an interface to the user whenaccessing payment provider server 134. In various embodiments where notprovided by transaction processing module 132, other applications 134may include connection and/or communication applications, which may beutilized to communicate information to over network 160.

Additionally, transaction management system 130 includes database 136.As previously discussed, the entity corresponding to merchant device 150may establish one or more payment accounts with transaction managementsystem 130. Payment accounts in database 136 may include entityinformation, such as name, address, birthdate, payment/fundinginformation, additional user financial information, and/or other desireduser data. The entity may link to their respective payment accountsthrough an account, user, merchant, and/or device identifier. Thus, whenan identifier is transmitted to transaction management system 130, e.g.,from communication device 110 and/or merchant device 150, a paymentaccount belonging to the entity may be found.

In various embodiments, transaction management system 130 includes atleast one network interface component 138 adapted to communicatecommunication device 110 and/or merchant device 150 over network 160. Invarious embodiments, network interface component 138 may comprise a DSL(e.g., Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency (RF), andinfrared (IR) communication devices.

Merchant device 150 may be maintained, for example, by a merchant havinga physical retail location where a user may purchase one or more items.In this regard, merchant device 150 may include a device havingprocessing applications, which may be configured to interact withcommunication device 110 and/or transaction management system 130 toengage in transactions. Merchant device 150 may be implemented using anyappropriate hardware and software configured for wired and/or wirelesscommunication with communication device 110 and/or transactionmanagement system 130. For example, in one embodiment, merchant device150 may be implemented as a single or networked personal computer (PC),a smart phone, laptop computer, wearable computing device, and/or othertypes of computing devices at a merchant location capable oftransmitting and/or receiving data. Although only one merchant device isshown, a plurality of merchant devices may function similarly.

Merchant device 150 of FIG. 1 contains a sales application 152, otherapplications 154, a database 156, and a communication module 158. Salesapplication 152 and other applications 154 may correspond to processes,procedures, and/or applications executable by a hardware processor, forexample, a software program. In other embodiments, merchant device 150may include additional or different modules having specialized hardwareand/or software as required.

Sales application 152 may correspond to one or more processes to executemodules and associated specialized hardware of merchant device 150 thatprovide checkout and payment processes for a transaction to purchase oneor more items for sale from the merchant corresponding to merchantdevice 150. In this regard, sales application 152 may correspond tospecialized hardware and/or software of merchant device 150 to provide aconvenient interface to permit a merchant to enter, view, and/or edititems and/or services for purchase by a user. For example, salesapplication 152 may be implemented as an application having a userinterface enabling the merchant to enter item information and requestpayment for a transaction on checkout/payment of one or moreitems/services. In certain embodiments, sales application 152 maycorrespond more generally to a web browser configured to viewinformation available over the Internet or access a websitecorresponding to the merchant and/or payment provider server 140. Thus,sales application 152 may provide item sales through an onlinemarketplace using the website of the merchant. Sales application 152 mayinclude a corresponding acceptance mechanism that is used to acceptpayment for a transaction and process the transaction by sending apayment request to transaction management system 130 and/orcommunication device 110. The acceptance mechanism may correspond todisplay or receipt of displayable codes, short range wirelesscommunications, location-based check-ins and determination of user ormerchant information, or other acceptance mechanism to accept anelectronic payment. Information on acceptance mechanisms may beretrievable by transaction management system 130 for purposes ofconfiguring payment application 120 of communication device 110 tointeract with sales application 152.

Once a payment amount is determined for a transaction for items to bepurchased by a user associated with communication device 110, salesapplication 152 may request payment from the user using the acceptancemechanism. The mechanism may correspond to a displayable code having anencoded token, digital credentials, digital token, and/or requiredinformation determined by communication device 110 and/or transactionmanagement system 130 for the payment instrument. Thus, the informationin the mechanism may be used to authenticate the user and allow forpayment. Sales application 152 may receive the mechanism from a scan ofa displayed code, entry of input of information, and/or receipt of ashort range wireless communication. Thus, sales application 152 may beused to scan the information, input the information using an inputdevice, image the information with a camera or video recorder, detectthe location, record an audio recording with a microphone, capture abiometric using a sensor, or otherwise input the information. Theprovided payment information may be communicated to transactionmanagement system 130 with the transaction and transaction informationby sales application 152 for approval. As discussed herein, paymentprovider server 150 may process the transaction with the provided tokenand determine whether to approve or decline the transaction using apayment instrument for the payment process used with the acceptancemechanism. Sales application 152 may then receive the results of thetransaction processing, and complete the transaction with the user, forexample, by providing the user the items for the transaction ordeclining the transaction where the user is not authenticated or thetransaction is not authorized (e.g., insufficient funds).

Merchant device 150 includes other applications 154 as may be desired inparticular embodiments to provide features to merchant device 150. Forexample, other applications 154 may include security applications forimplementing client-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 160, or other types of applications.Other applications 154 may also include email, texting, voice and IMapplications that allow a user to send and receive emails, calls, texts,and other notifications through network 160. In various embodiments,other applications 154 may include financial applications, such asbanking, online payments, money transfer, or other applicationsassociated with transaction management system 130. Other applications154 may contain software programs, executable by a processor, includinga graphical user interface (GUI) configured to provide an interface tothe user.

Merchant device 150 may further include database 156 which may include,for example, identifiers such as operating system registry entries,cookies associated with sales application 152 and/or other applications154, identifiers associated with hardware of merchant device 150, orother appropriate identifiers, such as identifiers used forpayment/user/device authentication or identification. Identifiers indatabase 156 may be used by a payment/credit provider, such astransaction management system 130, to associate merchant device 150 witha particular account maintained by the payment/credit provider. Database156 may further include transaction information and/or results.

Merchant device 150 includes at least one communication module 158adapted to communicate with communication device 110 and/or transactionmanagement system 130. In various embodiments, communication module 158may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency, infrared, Bluetooth, and near field communication devices.

Network 160 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 160 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 160 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2 is an exemplary geo-fenced merchant location to provide a userexperience on a mobile device, according to an embodiment. Inenvironment 200 of FIG. 2 , a fuel site is shown with a geo-fence sothat the user with their communication device is associated with thefuel site merchant when the user crosses the geo-fence. Moreover,environment 200 of FIG. 2 further includes communication device 110discussed in reference to environment 100 of FIG. 1 .

As shown in environment 200, a map 1000 may include one or more merchantlocations, such as a fuel location 1002 and a coffee location 1004. Inthis regard, users may wish to visit one or more of fuel location 1002and coffee location 1004 in order to transact with the merchant(s) topurchase one or more items. The users may wish to utilize a paymentapplication executing on a communication device. However, establishing aconnection and/or retrieving merchant information in order to provide apayment to one of the merchants may be time consuming and difficult, andthus, the users may choose to use other payment instruments, such ascash or a physical payment card.

In this regard, a payment provider (not shown) may configurecommunication device 110 based on detection of communication device 110at fuel location 1002 or coffee location 1004. By configuringcommunication device 110, a payment application executing oncommunication device 110 may be ready to checkout and pay for atransaction using payment acceptance mechanisms available at fuellocation 1002 or coffee location 1004. Thus, in order to determine wherea user is located at, the payment provider may receive a usergeo-location 1006. User geo-location 1006 is shown on map 1000.Moreover, the payment provider may associate user geo-location 1006 witha merchant through geo-fenced areas of the merchant. For example, map1000 further includes a geo-fencing 1008 around fuel location 1002.Thus, it may be determined that the user located at user geo-location1006 is at fuel location 1002 and ready to purchase fuel.

In this regard, the payment provider may determine one or more paymentacceptance mechanisms available at fuel location 1002. One suchacceptance mechanism may include payment through a payment applicationexecuting on communication device 110, for example, through short rangewireless communications (e.g., NFC between communication device 110 anda merchant device, such as a fuel pump), QR code/barcode scanning ofencoded payment information, and/or check-in and networked payments tothe merchant. Once an acceptance mechanism is selected, the paymentprovider may configure communication device 110 to utilize theacceptance mechanism and alert the user that the payment application ofcommunication device 110 is ready to transact with the merchant for fuellocation 1002. Thus, an interface 1010 of communication device 110 mayalert the user that a payment provider 1012 is reached to process atransaction 1014 and provide a payment to the merchant through thepayment application.

FIG. 3 is an exemplary system environment having a communication deviceconfigured to payment processing with a merchant device by a paymentprovider server based on accepted payment mechanisms for the merchantdevice, according to an embodiment. Environment 300 of FIG. 3 includes acommunication device 110, a transaction management system 130, and amerchant device 150 corresponding generally to described devices andassociated features found in system 100 of FIG. 1 .

Transaction management system 130 executes an acceptance mechanismapplication 140 corresponding generally to the specialized hardwareand/or software modules and processes described in reference to FIG. 1 .In this regard, acceptance mechanism application 140 may be used todetermine a payment acceptance mechanism for communication device 110 toutilize with merchant device 150 during transaction processing andgenerate a payment process to configure communication device 110 toutilize the payment acceptance mechanism. Thus, payment acceptanceapplication 140 includes application configurations 2000. Applicationconfigurations 2000 includes information for a user A 2002 correspondingto communication device 110 and a merchant A 2008 corresponding tomerchant device 150.

For example, user A 2002 includes information for payment application120 executing on communication device 110, such as processes andfeatures requiring configuration to utilize an acceptance mechanism usedby merchant device 150. Moreover, user A 2002 includes user data 2004,which includes at least a location 2006. In further embodiments, userdata 2004 may further include user preferences, purchase history,previous merchant locations visited, and/or user information. Merchant A2008 may include merchant data 2010 for matching to user data 2004. Forexample, merchant data 2010 includes a geo-fence 2012 for merchant A2008, such as an established area for merchant A 2008 that maycorrespond to a merchant location. Geo-fence 2012 may be matched tolocation 2006 for determination of whether user A 2002 is visitingmerchant A 2008. Merchant data 2010 further is associated with paymentdata 2014 for merchant A 2008, which includes acceptance mechanisms 2016for merchant A 2008 and merchant device 150.

Using the aforementioned information, acceptance mechanism application140 determines a matched user-merchant relationship 2018, which includesmerchant A and user A 2020. Matched user-merchant relationship 2018 maybe determined using user data 2004 and merchant data 2010 as discussedherein, by locating location 2006 within geo-fence 2012. Using matcheduser-merchant relationship 2018, a selected payment mechanism 2022 maybe determined. Selected payment mechanism 2022 may be used to determinepayment process 2024, which may configure communication device 110.

Communication device 110 executes a payment application 120corresponding generally to the specialized hardware and/or softwaremodules and processes described in reference to FIG. 1 . In this regard,payment application 120 may be used to process a payment after beingconfigured to interface with merchant device 150 using a payment processdetermined by transaction management system 130. Thus, paymentapplication 120 includes data for location 2006, which may betransmitted to transaction management system 130. Payment application120 further includes a configured payment process 2100, which mayinclude application interfaces and communication protocols for providinga payment to merchant device 140. Thus, configured payment process 2100includes transaction 2102 with merchant device 150 having a cost 2104.Payment application 120 may further be used to provide a token 2106 tomerchant device 150 or receive token 2106 from merchant device 150,which may include tokenized data 2108 used for payment processing, suchas an identifier associated with a user, merchant, payment instrument,digital wallet, or other identifying information.

Merchant device 150 executes a sales application 152 correspondinggenerally to the specialized hardware and/or software modules andprocesses described in reference to FIG. 1 . In this regard, salesapplication 152 may process token 2106 from communication device 110received using an acceptance mechanism determined by transactionmanagement system 130. In other embodiments, sales application 152 mayprovide token 2106 to communication device 110 for transactionprocessing. Thus, sales application 152 includes acceptance mechanisms2016, which may correspond to payment acceptance mechanisms that may beused with merchant device 150 to process a payment. Information foracceptance mechanisms 2016 may be communicated to transaction managementsystem 130 for use in determining payment process 2024. Moreover, salesapplication includes transaction 2102 with communication device 120having cost 2104. Transaction 2102 may be receive a payment instrumentand/or be processed through selected acceptance mechanism 2022, andreceive transaction results 2200 from transaction processing.

FIG. 4 is an exemplary process flowchart for automatic synchronizationof a device for transaction processing based on geo-fenced locations,according to an embodiment. Note that one or more steps, processes, andmethods described herein may be omitted, performed in a differentsequence, or combined as desired or appropriate.

At step 402, user data for a user and merchant data for a plurality ofmerchants is accessed, for example, by a payment provider system thatcomprises one or more hardware processors coupled to a non-transitorymemory. The user data may be generated from user actions by the user. Insuch embodiments, the user actions are determined by a communicationdevice in possession of the user. For example, the user actions maycomprise at least one of locations of the user, online search historiesby the user, biometrics of the user, messages sent and received by theuser, and financial transactions by the user.

A prospective merchant associated with the user is determined using theuser data and the merchant data, at step 404. The user data may comprisea geo-location of the user determined using a GPS locator of acommunication device for the user, wherein the prospective merchant isdetermined using the geo-location of the user. For example, the merchantdata may comprise a geo-fenced area for the prospective merchant,wherein the prospective merchant is determined by matching thegeo-location and the geo-fenced area. The user data may further comprisepast merchant locations visited by the user, wherein the prospectivemerchant is determined based on the past merchant locations visited bythe user. Additionally, the user data may comprise at least one of userpreferences set by the user and user information for the user, whereinthe merchant data comprises merchant information for the user, whereinthe user preferences comprise preferred merchant information for theuser, and wherein the user information comprises at least one ofpersonal information for the user and financial information for theuser.

At step 406, payment data for the prospective merchant is determined,wherein the payment data comprises at least one payment acceptancemechanism utilized by the prospective merchant at a merchant locationfor the prospective merchant. The payment data may comprise paymentprocessing devices utilized at the merchant location for the prospectivemerchant. A payment process used by the user with the prospectivemerchant location is configured using the payment data, for example,through a payment application of a communication device, at step 408.The payment process may comprise a payment application executing on acommunication device for the user. Thus, the payment application may beassociated with an online payment provider providing payment services tothe user, wherein the user utilizes a payment account with the onlinepayment provider to process payments through the payment application.The payment application may provide a payment to the prospectivemerchant using the payment process through the at least one paymentacceptance mechanism, and wherein the payment process utilizes one ofnear field communications (NFC) with a merchant device at the merchantlocation, display of a barcode or QR code on an output display device ofthe communication device, and location based check-in of the userthrough the communication device. Thus, the payment process comprises acheck-in at the merchant location by the user, wherein the check-in mayautomatically fill merchant information for the prospective merchantinto the payment process in a payment application executing on acommunication device of the user. The payment process may further alertthe prospective merchant of the user at the merchant location, andwherein the payment process further provides user information for theuser to a merchant device at the merchant location.

In various embodiments, a request to change the prospective merchantfrom the user is received. Additionally, at least one other nearbyprospective merchant is determined using the user data and nearbymerchant data for the at least one other nearby prospective merchant. Infurther embodiments, nearby merchant data for at least one nearbymerchant is accessed, and at least one other prospective merchantmatching the user data is determined using the nearby merchant data. Insuch embodiments, the at least one other prospective merchant iscommunicated to a communication device of the user for selection toreconfigure the payment process executed by the communication device. Invarious embodiments, the payment process further comprises at least oneof an advertisement for the prospective user communicated to acommunication device of the user and interface graphics of the merchantdisplayed through an application executing on the communication deviceof the user.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1 , according to an embodiment. Invarious embodiments, the communication device may comprise a personalcomputing device (e.g., smart phone, a computing tablet, a personalcomputer, laptop, a wearable computing device such as glasses or awatch, Bluetooth device, key FOB, badge, etc.) capable of communicatingwith the network. The service provider may utilize a network computingdevice (e.g., a network server) capable of communicating with thenetwork. It should be appreciated that each of the devices utilized byusers and service providers may be implemented as computer system 500 ina manner as follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another communication device, service device, or aservice provider server via network 160. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 512, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via a communicationlink 518. Processor(s) 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A system, comprising: a non-transitory memorycomprising instructions; and one or more hardware processors coupled tothe non-transitory memory and configured to read the instructions tocause the system to perform operations comprising: detecting an entry ofa user device of a user into a first geo-fenced area of a merchant basedon at least one of signal from a GPS locator of the user device or anapplication check-in by the user device with an online computingservice; based on the detecting: identifying merchant information thatis associated with the first geo-fenced area and a merchant deviceassociated with the first geo-fenced area; determining, based on themerchant information, a first payment acceptance mechanism of aplurality of payment acceptance mechanisms available via a mobileapplication executing on the user device for use with the merchantdevice in the first geo-fenced area; outputting an alert to the user inthe mobile application on the user device of the first paymentacceptance mechanism available for use with the merchant device in thefirst geo-fenced area; auto-populating one or more fields in the mobileapplication with the merchant information for the first paymentacceptance mechanism; and processing a transaction using the firstpayment acceptance mechanism based on the auto-populated one or morefields.
 2. The system of claim 1, wherein the detecting the entrycomprises detecting a wireless connection between the user device and awireless transceiver associated with the first geo-fenced area, andwherein the operations further comprise: outputting the plurality ofpayment acceptance mechanisms available via the mobile application whilethe user device is within the first geo-fenced area.
 3. The system ofclaim 2, wherein the auto-populating the one or more fields comprises:communicating with the user device via the wireless transceiver;receiving a selection of the first payment acceptance mechanism; andloading the one or more fields in the mobile application with themerchant information based on the communicating.
 4. The system of claim1, wherein the first payment acceptance mechanism comprises one of adisplayable code comprising encoded data for a payment token of the useror a wireless token communication mechanism for the payment token. 5.The system of claim 1, wherein the merchant information entered to theone or more fields comprises at least one of a merchant accountidentifier for the merchant, a user account identifier for a useraccount of the user with the system, or payment authorization data for apayment made via the user account of the user.
 6. The system of claim 1,wherein the first geo-fenced area comprises a portion of at least twogeo-fenced areas for the merchant, and wherein the one or more fieldsare auto-populated with the merchant information that is specific to thefirst geo-fenced area and the merchant device from the at least twogeo-fenced areas.
 7. The system of claim 1, wherein the operationsfurther comprise: determining an offer associated with the firstgeo-fenced area or the merchant; and providing the offer to the userdevice with the alert based on the detecting.
 8. A method, comprising:detecting that a user is located within a first geo-fenced areaassociated with a merchant based on one or more operations executed by auser device of the user; accessing merchant data of the merchant basedon the detecting; determining, based on the merchant data, a pluralityof payment processing mechanisms available at the first geo-fenced areato the user device for use between a merchant device of the merchant anda mobile application on the user device; alerting the user, through themobile application, of the plurality of payment processing mechanismsavailable at the first geo-fenced area; receiving a selection of a firstpayment processing mechanism of the plurality of payment processingmechanisms for the mobile application; configuring the mobileapplication to utilize the first payment processing mechanism whilewithin the first geo-fenced area, wherein the configuring comprises:entering at least a portion of merchant information for the merchant toone or more fields of the mobile application executing on the userdevice for the first payment processing mechanism; and processing atransaction using the first payment acceptance mechanism based on thepopulated one or more fields.
 9. The method of claim 8, wherein thedetecting comprises detecting a wireless connection between the userdevice and a wireless transceiver of the merchant device, and whereinthe alerting the user of the plurality of payment processing mechanismsincludes identifying a payment provider associated with each of theplurality of payment processing mechanisms for processing a payment tothe merchant device for a transaction within the first geo-fenced area.10. The method of claim 9, wherein the entering comprises loading theone or more fields of the mobile application with the at least theportion of the merchant information via the wireless connection.
 11. Themethod of claim 8, wherein the first payment processing mechanismcomprises one of a displayable code comprising encoded data for apayment token of the user or a wireless token communication mechanismfor the payment token.
 12. The method of claim 8, further comprising:receiving, via the mobile application, an electronic transactionprocessing request between the user and the merchant that is associatedwith the first geo-fenced area, wherein the electronic transactionprocessing request comprises the at least the portion of the merchantinformation; and processing the electronic transaction processingrequest using a user account of the user that is associated with themobile application.
 13. The method of claim 12, wherein the processingthe electronic transaction processing request comprises communicating adigital token to the merchant device for the user account.
 14. Themethod of claim 8, further comprising: automatically displaying, via themobile application, an offer to the user that is associated with atleast one of the merchant or the first geo-fenced area.
 15. Anon-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause a machine to performoperations comprising: detecting a user device of a user that is locatedwithin a geo-fenced area associated with a merchant location of amerchant using at least one of data from a GPS locator of the userdevice or application data from an application on the user device;determining merchant device data for a merchant device within thegeo-fenced area, wherein the merchant device data comprises merchantdevice capabilities for the merchant device; determining, based on themerchant device data, a plurality of payment processing mechanismsavailable for use between the merchant device and the application on theuser device; and based on the determining the plurality of paymentprocessing mechanisms: notifying the user in the application of theplurality of payment processing mechanisms; receiving a selection of apayment processing mechanism of the plurality of payment processingmechanisms; communicating with the merchant device to configure themerchant device and the application on the user device for the paymentprocessing mechanism; automatically filling merchant data for themerchant device in the application on the user device; and processing atransaction using the first payment acceptance mechanism based on theautomatically populated one or more fields.
 16. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: causing the application to communicate with the merchantdevice over a short-range wireless communication, wherein theapplication provides a digital payment token to the merchant device viathe short-range wireless communication.
 17. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: transmitting an alert to the merchant device of the userlocated within the geo-fenced area of the merchant location.
 18. Thenon-transitory machine-readable medium of claim 17, wherein theoperations further comprise: loading, with the alert, user informationof the user to the merchant device, wherein the user informationincludes at least one of user identification information of the user ora digital payment token associated with the user.
 19. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: providing an offer to the user device for use at the merchantlocation based on the detecting the user device that is located withinthe geo-fenced area.
 20. The non-transitory machine-readable medium ofclaim 15, wherein the payment processing mechanism comprises one of adigital image having encoded data for a payment token of the user or awireless communication protocol for the payment token.